Methods and Apparatus for Controlling Signalling Gateways

ABSTRACT

A method is described for operating a signalling gateway comprising determining information enabling an application server to identify a signalling gateway process to which to direct a message destined for a particular point code and making said information available to the application server. In preferred embodiments, the information takes the form of a routing table that serves to distribute signalling gateway process identifiers over possible SLS values by, for instance, mapping process instance identifiers to possible SLS values for messages sent by the application server. By allowing the application server processes the possibility to determine to which signalling gateway process each message should be directed, retransmission of messages within the signalling gateway can be avoided.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The invention relates to methods, and related apparatus, for controlling processing entities used, for instance, in communication systems such as for the control of signalling traffic between a signalling gateway and a plurality of application server processes.

2. Background Art

Establishing connections between two telephones involves a complex interaction of digital messages, hereinafter referred to generally as signalling. Nowadays telephone systems perform what is known as “out-of-band” signalling. Out-of-band signalling means that the communications required between the switches and other equipment in the network take place on communication channels other than the channel by which the voice or data flows. Typically, the out-of-band signalling takes place by means of digital communication channels. Thus, the public switch telephone network (PSTN) generally uses two types of channels, media and signalling.

Several protocols have been defined for out-of-band signalling. The most commonly used protocol, in North America, Asia and Europe, is known as Signalling System No. 7 (SS7). However, the SS7 protocol defines more: than just a protocol for communication between switches. It also defines an entire switching network for facilitating signalling for call establishment, routing, and information exchange functions of switched circuit networks.

Since the amount of data transferred over data networks is now much larger than the voice traffic that is carried over the PSTN, carriers are in the process of consolidating both types of networks. In addition, telecommunication networks are increasingly making use of standard computing hardware in order to reduce IT costs.

Therefore, there is a trend in the telephone industry to migrate telephone systems using SS7-based networks for signalling to Internet Protocol (IP) networks. The Internet protocols are standardised by the Internet Engineering Task Force (IETF). Moving either or both of the media and signalling channels to an IP infrastructure involves the use of very different technologies and can be done independently. The SIGTRAN IETF working group is currently in the process of defining the protocols for back-hauling SS7 signalling messages across IP networks. Generally speaking, signalling across an IP network involves replacing the lower levels of the SS7 layered protocol communications and transport layers with IP network protocol communications and transport layers.

The SIGTRAN group have taken the initiative to define open standards for transporting SS7 over IP networks. With SIGTRAN technology, telephone services which today lie on top of SS7 networks, can run Application Servers (ASs) lying on top of IP networks. The interworking with SS7 networks is performed by SIGTRAN signalling gateways (SGs).

For additional information regarding SS7 network switching over IP networks, reference may be made to the (IETF) working drafts “Signalling Connecting Control Part User Adaptation Layer (SUA)” available from the IETF website at www.ietforg, and IETF RFC 3332 “SS7 MTP3—User Adaptation Layer (M3UA)”, available from the IETF website, and which are both incorporated herein by reference as if reproduced in full. It is noted that the SUA document is a work in progress and is therefore subject to, change. However, these documents, which will be referred to herein as the SIGRAN documents, exemplify the changes necessary to a standard SS7 signalling system for its implementation in an IP network context. As well as defining the functions of signalling gateways and signalling gateway processes, the SIGTRAN documents referred to above specify in detail the protocols to be implemented between a signalling gateway and a application server.

For more general background information regarding SIGTRAN protocols, reference may be made to the International Engineering Consortium, in document “SS7 Over IP Signalling Transport and SCTP,” which is available from the IEC website www.iec.org, and which is incorporated herein by reference as if reproduced in full.

To enhance the availability of the signalling gateway, it can be distributed over several processes running in one or several computers, each of them being a Signalling Gateway Process (SGP). Every SGP belonging to a particular SG has the same SS7 point code (or the same list of PCs), with each SGP generally being connected to the SS7 network through redundant links that are selected in conventional manner via Signalling Link Selector (SLS) values present in the SS7 messages.

On the IP network side, each SGP is connected to the ASPs running the services. Each AS, which can typically be identified with a single logical service, such as a Short Message Service Centre (SMSC), can also be implemented in a distributed manner by one or more processes or computers—referred to as the ASPs. To provide improved reliability, each SGP is typically directly connected to each ASP through an Stream Control Transfer Protocol (SCTP) association such that there is one association between each SGP and each ASP.

However, the use of redundant links to the SS7 network, which is highly desirable to ensure fault tolerance of the gateway, can result in latency and performance inefficiencies within the gateway since signalling messages may need to be transmitted between elements of the gateway itself in order to reach signalling unit hardware which carries an outbound SS7 link selected in accordance with an SLS value of a message.

It is an object of the present invention to overcome this and/or other drawbacks with the prior art.

SUMMARY OF THE INVENTION

In brief, the present invention provides a method for operating a signalling gateway comprising determining information enabling an application server to identify a signalling gateway process to which to direct a message destined for a particular point code and making said information available to the application server.

In preferred embodiments, the information takes the form of a routing table that serves to distribute signalling gateway process identifiers over possible SLS values by, for instance, mapping process instance identifiers to possible signal link selector values for messages sent by the application server.

Thus, an application server can obtain more specific information enabling it to determine directly a signalling gateway process to which to transmit messages destined for a particular point code. With use of a distributed gateway architecture where signalling links are distributed over redundant hardware, the SGPs can be hosted so as to each have direct access to signalling unit hardware for a subset of the signalling links. By allowing the application server processes the possibility to determine to which SGP each message should be directed, retransmission of messages within the signalling gateway can be avoided.

In preferred embodiments, the signalling gateway can be responsive to a change in the status of links upon a route to a particular point code to recalculate the routing table for that point code and transmit the recalculated routing table to an application server in a further message. In this way, it can be provided that the ASPs select SGPs on the basis of the SLS values taking into account the availability or not of the signalling links to which each SGP has direct access.

In an SS7 network, the routing decisions are taken by the signalling network management functions of the MTP3 layer. Whenever a change in the status of a signalling link, route or point code occurs, 3 different signalling network management functions (ie signalling traffic management, link management and route management) are activated. However, only a subset of the routing information gathered by the MTP3 layer is transmitted to the remote AS SIGTRAN layer (M3UA or SUA as the case may be). In the systems envisaged by the SIGTRAN documents, only the status of the remote Point Code (“available”, “restricted” from SG point of view, or “not available”) is reported to the remote AS. The Signalling Gateway maintains the status (availability, restriction, and/or congestion of route to destination) of the individual routes, derives the overall availability or congestion status of the destination from the status of the individual routes, and informs the ASP of this derived status whenever it changes. In at least preferred embodiments, the routing table is included in this message transmitted from an SGP to an ASP that serves to indicate the accessibility of the point code concerned in accordance with the SIGTRAN documents, a separate routing table being established for each destination point code.

Other aspects of the invention provide methods for operating a corresponding application server process, signalling gateway elements and application server elements arranged to carry out the above described methods and a signalling gateway having a redundant set of signalling links to a signalling network and having a single point code, or set of point codes, therein, and comprising a plurality of such signalling elements, with each signalling element comprising a signalling unit to which a subset of the signalling links are connected.

BRIEF DESCRIPTION OF THE DRAWINGS

An embodiment of the invention will now be described, by way of example only, with reference to the accompanying drawings in which:

FIG. 1 shows the general configuration of a signalling gateway;

FIGS. 2 a and 2 b illustrate the layered protocol communications schemes of a Signalling End Point, a Signalling Gateway Process and an Application Server Process;

FIG. 3 illustrates associations between Signalling Gateway processes and Application Server processes and signalling connections to point codes;

FIG. 4 shows an exemplary sequence of events and signalling network management message exchanges;

FIG. 5 illustrates the main processes that carried out by signalling gateway processes in order to implement this invention;

FIG. 6 illustrates steps of a process carried out by an application server process in order to send a message.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

FIG. 1 shows the general configuration of a signalling gateway 100 interconnecting an SS7 network 110 and a series of Application Servers (ASs) 130 via an IP Network 120. FIGS. 2 a and 2 b illustrate the layered protocol communications architecture of the various components. SS7 Signal Transfer Point (STP) or Signal End Point (SEP) 200 includes the MTP1, MTP2, MTP3, SCCP and SCCP user part layers. As is known in the prior art, a Signal Transfer Point (STP) or Signal End Point (SEP) 200 routes SS7 signalling within the SS7 network and manages various signalling links which comprise the SS7 network. Routing is accomplished by processing of the routing label of an SS7 message by the Message Transfer Part (MTP) functionality. The MTP layers comprise three levels. Levels 1 and 2 are used for the transfer of SS7 messages from one point to another over an individual signalling link. Level 3 is used for the transfer of SS7 messages over the SS7 network beyond the requirements of individual link transmission. The MTP3 layer is mainly dedicated to ensuring the delivery of incoming and outgoing messages (such as discrimination, distribution and routing), and the network reconfiguration (such as traffic management, route management and link management).

Communication between Signalling Gateway Processes (SGPs) of the SG 100 and Application Server Processes (ASPS) within the ASs 130 is carried out using a transport layer defined by the SIGTRAN working group and referred to as SCTP (Stream Control Transfer Protocol) which is defined in RFC 3309. Signalling Gateway 100 terminates the MTP1, MTP2, MTP3 and SCCP layers and includes a Nodal Interworking function (NIF) as well as SUA, SCTP and IP layers. Each AS 130 includes IP, SCTP, SUA and SCCP user layers. Signalling Gateway 100 thus terminates the SS7 lower layers and encapsulates their payload data into SCTP messages to send them to an Application Server 130. The AS terminates the SCTP layers, processes the signalling messages and replies to the SG 100 in the same way. In the case of SS7 and M3UA interworking, the M3UA adaptation layer is designed to provide an extension of the MTP3 layer as shown in FIG. 2 b.

These architectures are well known to those skilled in the relevant art and are described in the SIGTRAN documents, referred to above.

FIG. 3 illustrates the interconnection of a plurality of SGPs, such as SGP1 and SGP2 to a plurality of ASPs, such as ASP1, ASP2 and ASP3 via a plurality of SCTP associations 300. The architecture is such that each SGP is hosted in a machine that contains the signalling units that provide only a subset of the MTP2 signalling links to SS7 network 110 available on the SG.

On the SS7 network, the routing decisions are taken by the signalling network management functions of the MTP3 layer. Whenever a change in the status of a signalling link, route or points occurs, 3 different signalling network management functions (ie signalling traffic management, link management and route management) are activated. The protocols defined in the SIGTRAN documents provide for a subset of the routing information gathered by the MTP3 layer to be transmitted to the remote AS SIGTRAN layer (M3UA or SUA as the case may be). Basically, only the status of the remote Point Code (“available”, “restricted” from SG point of view, or “not available”) is reported to the remote AS by means of DUNA (destination unavailable), DRST (destination restricted), DAVA (destination available) SIGTRAN messages respectively.

The DUNA message is sent from an SGP in an SG to all concerned ASPs to indicate that the SG has determined that one or more SS7 destinations are unreachable. It is also sent by an SGP in response to a message from the ASP to an unreachable SS7 destination. As an implementation option the SG may suppress the sending of subsequent “response” DUNA messages regarding a certain unreachable SS7 destination for a certain period to give the remote side time to react. If there is no alternate route via another SG, the MTP3-User at the ASP is expected to stop traffic to the affected destination via the SG as per the defined MTP3-User procedures.

The DUNA message contains the following parameters:

-   -   Network Appearance Optional     -   Routing Context Optional     -   Affected Point Code Mandatory     -   INFO String Optional

The optional INFO String parameter is defined so as to be able to carry any meaningful UTF-8 character string along with the message. The length of the INFO String parameter is from 0 to 255 octets. No procedures are specifically identified in the SIGTRAN documents for its use but it is suggested that the INFO String may be: used for debugging purposes. The DRST, DAVA and DAUD messages have similar formats.

In the case of a distributed Signalling Gateway in which each SGP is hosted in a machine that contains the signalling units that provide only a subset of the MTP2 signalling links to SS7 network 110 available on the SG, the information available on the AS side, and provided by the SIGTRAN (M3UA or SUA) layer in accordance with the protocols described in the SIGTRAN documents is therefore not sufficient to allow an ASP to identify the SGP that contains the SS7 signalling link that corresponds to a particular SLS value for a given destination point code. Thus if the ASP sends a message to an SGP that does not contain the right signalling link, the selected SGP must in a separate step forward the message within the SG to the SGP that does contain the signalling link.

A protocol will be described below which is based on messages embedded in the SIGTRAN messages by means of the usage of “info string” field. By taking advantage of this extra information, the ASPs are able to determine the SGP that contains the signalling link, on which the message must be forwarded, directly.

The protocol, which will be referred to as RSIG in this document, is implemented by 4 messages:

ROUTING_INFO_CAPABILITY_REQ

This message is sent from the ASP to the SGP embedded in an ASP_ACTIVE SIGTRAN message to determine whether the remote SGP supports the RSIG protocol, to gather the RSIG identifier of the remote SGP and to indicate that this ASP may request RSIG information from the SGP. The ASP sends this message to Bach SGP in the SG in order to collect all the RSIG IDs.

ROUTING_INFO_CAPABILITY_ACK

This message is sent from the SGP to the ASP, in an ASP-ACTIVE-ACK SIGTRAN message in response to a received ROUTING_INFO_REQ message, to indicate that the SGP supports the RSIG protocol and that the SGP authorizes the ASP to gather RSIG information and to report the SGP's RSIG identifier.

ROUTING_TABLE

This message is sent by an SGP to the ASP, in a DAVA SIGTRAN message to indicate the routing (for each SLS) for a particular destination.

ROUTING_INFO_REQ

This message is sent by an ASP to the SGF, in a DAUD SIGTRAN message to indicate that as part of the audit of the specified destination, the routing table is requested. The DAUD message is defined in the SIGTRAN protocols to be sent from the ASP to the SGP to audit the availability or congestion state of SS7 routes from the SG to one or more affected destinations. The format and description of DAUD Message parameters is the same as for the DUNA message described above. This message has an immediate effect in the sense that the routing table corresponding to the audited PC is made immediately available by the SGP (by means of a DAVA containing a RSIG ROUTING_TABLE message) but it also indicates, in the SGP, that each time an event occurs that affects the routing of the PC concerned, the SG must inform the ASP. By this means, the information sent: by the SGPs to the ASPs is limited to the set of remote PC's that each ASP needs to handle.

As “info string” field must be contain only ASCII characters, the messages of the RSIG protocol are based on ASCII only and are described by the following ABNF grammar (see RFC2234) description: RSIGMessage = RSIGToken SLASH Version SEP messageBody messageBody = 1*1( RoutingInfoCapabilityReq /  RoutingInfoCapabilityAck /  RoutingTable /  RoutingInfoReq ) RoutingInfoCapabilityReq = RoutingInfoCapabilityReqToken EQUAL LBRKT RBRKT RoutingInfoCapabilityAck = RoutingInfoCapabilityAckToken EQUAL LBRKT RICAParameters RBRKT RoutingTable = RoutingTableToken EQUAL LBRKT SLSTable RBRKT RoutingInfoReq = RoutingInfoReqToken EQUAL LBRKT RIRParameters RBRKT RICAParameters = RICASGPId COMMA RICAResult RICASGPId = RICASGPIdToken EQUAL 1*3(DIGIT) RICAResult = ResultToken EQUAL RICAResultValue RIRParameters = RIRInfo RIRInfo = RIRInfoToken EQUAL RIRInfoEnableToken SLSTable = (SLSITUTable / SLSANSITable) SLSITUTable = SLSITUTableToken EQUAL LBRKT SLSITUTableResult RBRKT SLSANSITable = SLSANSITableToken EQUAL LBRKT SLSANSITableResult RBRKT RICAResultValue = 1*2(DIGIT) ; today 2 values are defined: ; => 1 : OK, the capability is supported ; => 2 : KO, the capability is not supported SLSITUTableResult = 16*16(1*3(DIGIT) COMMA) 1*3(DIGIT) SLSANSITableResult = 32*32(1*3(DIGIT) COMMA) 1*3(DIGIT) Version = 1*2(DIGIT) ; today, only version 1 is defined DIGIT = %x30-39 ; 0-9 SLASH = %x2F  ; “/” SP = %x20 ; space HTAB = %x09 ; horizontal tab CR = %x0D ; Carriage return LF = %x0A ; linefeed EOL = (CR [LF] / LF ) WSP = SP / HTAB ; white space SEP = ( WSP / EOL) LWSP = *( WSP / EOL ) LBRKT = LWSP %x7B LWSP ; “{” RBRKT = LWSP %x7D LWSP ; “}” COMMA = LWSP %x2C LWSP ; “,” EQUAL = LWSP %x3D LWSP ; “=” RSIGToken = (“RSIG”) RICASGPIdToken = (‘‘RICASGPID’’ / ‘‘RICASI’’) RIRInfoToken = (‘‘RIRI’’) RIRInfoEnableToken = (‘‘OFF” / ‘‘ON’’) RoutingInfoCapabilityReqToken = (‘‘RICR’’) RoutingInfoCapabilityAckToken = (‘‘RICA’’) RoutingTableToken = (‘‘RT’’) RoutingInfoReqToken = (‘‘RIR’’) ResultToken = (‘‘RES” / ‘‘R’’) SLSITUTableToken = (‘‘SLSITUTAB” / ‘‘SIT’’) SLSANSITableToken = (‘‘SLSANSITAB’’ / ‘‘SAT’’)

It will be appreciated that a decoder of such a grammar can be readily implemented with commonly available tools.

In the following, an example will be given of behaviour for the system illustrated in FIG. 3 with an ASP and a SG 100 composed of 2 SGPs, SGP1 and SGP2. SGP1 and SGP2 are shown as being hosted on physically separate hardware platforms interconnected by an internal local area network. Each component is assumed to be configured to make use of the RSIG protocol.

The exemplary SS7 topology shown in FIG. 3 is as follows: SGP1 contains 2 signalling links: link 11 and Link 21; SGP2 contains 2 signalling links: link 12 and link 22. SG 100 is connected to PC 10 by linkset 1 and to PC 11 by linkset 2. A linkset is a number of signalling links that directly interconnect two signalling points and which are used as a module—links within the linkset being selected by means of a the SLS values in each message. It will be understood that the separate signalling links within the linksets are generally always distributed over different SGPs for redundancy reasons.

The SG 100 is connected in associated mode to 2 adjacent nodes: PC 10 and PC 11. In this example, two other remote point codes, are also available on the network: PC 20 and PC 21. Each of them is reachable via 2 routes. The network is assumed for the purposes of example to be an ITU network.

An exemplary sequence of events and signaling network management message exchanges is shown in FIG. 4 and the main processes used in signalling gateway 100 are illustrated in FIG. 5.

Initially the ASP signals in conventional planner to the SGP1 and SGP2 that it is up using respective ASP_UP messages which are acknowledged by ASP_UP_ACK messages as shown in FIG. 4.

The use of the RSIG protocol to pass routing information between ASP 130 and SGP1 and SGP2 will now be described in relation to steps 500 to 590 as follows.

Step 500: When the ASP is able to handle traffic it informs SGP1 by sending an ASP_ACTIVE message in which a ROUTING_INFO_CAPABILITY_REQ message is embedded. The ROUTING_INFO_CAPABILITY_REQ message is formatted as follows:

RSIG/1

RICR={ }

where RSIG is the ABNF string used to identify the RSIG protocol, 1 is the version of RSIG, RICR is the ABNF string used to identify a ROUTING_INFO_CAPABILITY_REQ RSIG message.

Step 510: SGP1 replies to ASP 100 using an ASP_ACTIVE_ACK message in which is embedded an ROUTING_INFO_CAPABILITY_ACK message. SGP1 has the RSIG capability, and thus it authorizes the ASP to take advantage of this capability and it informs the ASP that its RSIG identifier is 111. The ROUTING_INFO_CAPABILITY_ACK message is formatted as follow: RSIG/1 RICA = { RICASI = 111, R = 1 } where RSIG is the ABNF string used to identify the RSIG protocol, 1 is the version of RSIG, RICA is the ABNF string used to identify a ROUTING_INFO_CAPABILITY_ACK RSIG message, RICASI indicates an SGP Identifier (value: 111), R indicates the result (value: 1, meaning that it is OK).

The SGP identifiers are allocated and managed by one of the SGPs which is designated a “master” SGP in any suitable way.

This registration process is illustrated by functionality 600 in FIG. 5 which is present in each SGP. In the example of FIG. 4, the registration process is then repeated for SGP2, as follows.

Step 520: ASP 100 informs SGP2 of its ability to handle traffic using a ASP_ACTIVE message in which is embedded an ROUTING_INFO_CAPABILITY_REQ message to check that SGP2 has the RSIG capability.

This second ROUTING_INFO_CAPABILITY_REQ message is formatted as follow: RSIG/1 RICR = { }

Step 530: SGP2 replies to ASP 100 using a ASP_ACTIVE_ACK message in which is embedded an ROUTING_INFO_CAPABILITY_ACK message. It has the RSIG capability, it authorizes the ASP to take advantage of this capability and it informs the ASP that its RSIG identifier is 222.

The ROUTING_INFO_CAPABILITY_ACK message from SGP2 is formatted as follow: RSIG/1 RICA = { RICASI = 222, R = 1 }

Next a destination query process, illustration by functionality 620 in FIG. 5 is carried out in relation to a particular destination point code selected by ASP 130. Within SG 100 each SGP maintains a routing table for each SS7 destination linking SLS values, SGP IDs and signalling link identifiers. These routing tables are updated internally to SG 100 based on information received from the SS7 network. In one embodiment for instance, whenever a TFP/TFA or TFR message is received from the SS7 network or a local signalling link changes status, each SGP forwards this information to the designated “master” SGP which can serialise the recalculation of the routing tables and their broadcast to each SGP.

Step 540: ASP 130 wants to AUDIT the SS7 remote destination 20. It sends an SIGTRAN DAUD message for this Point Code and informs SGP1 that it wants to be notified of routing changes by including a ROUTING_INFO-REQ message in the DAUD message. This information is distributed internally by the SG to all SGPs.

The ROUTING_INFO_REQ message is formatted as follow: RSIG/1 RIR = { RIRI = ON } where RSIG is the ABNF string used to identify the RSIG protocol, 1 is the version of RSIG, RIR is the ABNF string used to identify a ROUTING_INFO_REQ RSIG message, RIRI indicates if the ASP wants to enable or disable the RSIG feature for this destination (value ON: feature is enabled).

Step 550: Immediately, SGP1 retrieves the routing table for the destination and reports the status of the SS7 remote destination 20 (as specified in the SIGTRAN procedure) and includes the routing information in the DAVA message using a first embedded ROUTING_TABLE RSIG message.

The first ROUTING_TABLE message in this example is formatted as follows (for the ITU case where the SLS has 4 bits): RSIG/1 RT = { SIT = { 111, 222, 111, 222, 111, 222, 111, 222, 111, 222, 111, 222, 111, 222, 111, 222 } } where RSIG is the ABNF string used to identify the RSIG protocol, 1 is the version of RSIG, RT is the ABNF string used to identify a ROUTING_TABLE RSIG message, SIT indicates an ITU Routing Table.

This first ROUTING_TABLE message indicates to ASP 130 that, to reach the remote destination 20, it is optimal for the ASP to take the decisions shown in Table 1 according to the SLS value of the MSU. TABLE I SLS value SGP 0 SGP1 (RSIG Id: 111) 1 SGP2 (RSIG Id: 222) 2 SGP1 (RSIG Id: 111) 3 SGP2 (RSIG Id: 222) 4 SGP1 (RSIG Id: 111) 5 SGP2 (RSIG Id: 222) 6 SGP1 (RSIG Id: 111) 7 SGP2 (RSIG Id: 222) 8 SGP1 (RSIG Id: 111) 9 SGP2 (RSIG Id: 222) 10 SGP1 (RSIG Id: 111) 11 SGP2 (RSIG Id: 222) 12 SGP1 (RSIG Id: 111) 13 SGP2 (RSIG Id: 222) 14 SGP1 (RSIG Id: 111) 15 SGP2 (RSIG Id: 222)

In the following steps, various routing change scenarios will be described and, in each case, a routing change process 620 is carried out. Process 620 basically comprises 3 steps—detection the routing change, recalculation of the routing tables and communication of the updated routing tables to ASP 130 embedded in DAVA messages. As before in some embodiments each SGP may forward routing change information to the designated “master” SGP which recalculates the routing tables and broadcasts them to each SGP. Alternatively, the routing tables could be recalculated within the SGP that first detects the routing change event and broadcasted by that SGP to all the other SGPs. The DAVA messages including the updated routing tables may be sent out to ASP 130 by any of the SGPs and so any suitable and/or convenient mechanism for selecting an SGP to respond may be used, such as having the master SGP respond (if there is one), having the SGP that detects the routing change respond, or having the SGP that originally received the ROUTING_INFO_REQ message from the SGP. Of course, in some embodiments all necessary routing tables may be calculated, configured or otherwise determined in advance and stored for a set of potential routing changes.

Step 560: In this example, it is imagined that SGP1 detects for instance that signalling link 11 is no longer operational for whatever reason, and implements a routing change. ASP 130 has requested to be notified for routing changes to destination 20 only, so SGP1 informs ASP with a DAVA message containing a recalculated second ROUTING_TABLE RSIG message, formatted as follows:  SIG/1 RT = { SIT = { 222, 222, 222, 222, 222, 222, 222, 222, 222, 222, 222, 222, 222, 222, 222, 222 } }

This second routing table indicates to ASP 130 that for all values of the SLS field in the MSU it is optimal for the ASP to send the MSU to SGP2 (RSIG ID 222).

Step 570: Now for the purposes of example, imagine that SGP2 receives, on the SS7 network side, a transfer prohibited (TFP) signal indicating that the first route (linkset 1) is unavailable for destination 20. The receipt of this message results in recalculated routing tables being broadcast to all SGPs and SGP1 informs ASP 130 with a DAVA message containing a third ROUTING_TABLE RSIG message, formatted as follows:

RSIG/1 RT = { SIT = { 111, 222, 111, 222, 111, 222, 111, 222, 111, 222, 111, 222, 111, 222, 111, 222 } }

This third ROUTING_TABLE message indicates to ASP 130 that, to reach the remote destination 20, it is once again optimal for the ASP to take the decisions shown in Table 1 according to the SLS value of the MSU.

Step 580: Now for the purposes of example, imagine that SGP1 receives, on the SS7 network side, a transfer prohibited (TFP) signal indicating that the second route (linkset 2) is unavailable for destination 20. Consequently, destination 20 is now not accessible. So SGP1 informs ASP with a DUNA message which does not contain any RSIG information since no routing table is necessary—the destination being not accessible.

Step 590: SGP1 receives, on the SS7 network side, a transfer allowed (TFA) signal indicating that the second route (linkset 2) is now available for destination 20. So SGP1 informs ASP with a DAVA message containing a fourth ROUTING_TABLE RSIG message, formatted as follows:

RSIG/1 RT = { SIT = { 111, 222, 111, 222, 111, 222, 111, 222, 111, 222, 111, 222, 111, 222, 111, 222 } }

This fourth ROUTING_TABLE message indicates to ASP 130 that, to reach the remote destination 20, it is once again optimal for the ASP to take the decisions shown in Table 1 according to the SLS value of the MSU.

FIG. 6 illustrates the process carried out by application server process 130 in order to send a signalling message. First the SLS value is extracted from the message in step 630, then the routing table is accessed in step 640 and a SGP identifier is determined based on the SLS value and the values of the routing table. The message is then sent on the SCTP association corresponding to the SGP identifier in step 650.

It will be appreciated that the present embodiments take the form of a set of computer programs intended for use with general purpose computing and signalling platforms and which may be marketed in the form of suitable computer program products including the functionality described. It will be appreciated that the invention may equally be implemented as special purpose hardware or any combination of software and hardware.

Although a specific embodiment of the invention has been described, the invention is not to be limited to the specific arrangement so described. The invention is limited only by the claims. 

1. A method for operating a signalling gateway process comprising determining routing information enabling an application server process to identify a signalling gateway process to which to direct signalling messages destined for a particular point code and making said information available to the application server process.
 2. A method as claimed in claim 1 wherein the information takes the form of a routing table that serves to distribute signalling gateway process identifiers over possible signalling link selector values included in signalling messages sent by the application server process.
 3. A method as claimed in claim 1 comprising responding to a change in the status of links upon a route to a particular point code by redetermining the routing information for that point code and making the redetermined information available to an application server process.
 4. A method as claimed in claim 1 wherein the determined routing information is made available to the application server process in response to receipt of an audit message from the application server process for a particular destination point code.
 5. A method as claimed in claim 3 wherein the determined and/or redetermined routing information is included in a message transmitted from a signalling gateway process to an application server process that serves to indicate the availability of the point code concerned.
 6. A method as claimed in claim 1 including a registration step comprising transmitting a signalling gateway process identifier to an application server process.
 7. A method as claimed in claim 6 wherein the signalling gateway process identifier is included in an acknowledgement by the signalling gateway process of a message indicating that the application server process is ready to receive signalling traffic.
 8. A method for operating an application server process to sending signalling messages to a signalling network via signalling gateway comprising a plurality of signalling gateway processes, the method comprising identifying a signalling gateway process to which to direct signalling messages destined for a particular point code by reference to routing information received from a signalling gateway process and SLS values contained in the signalling messages.
 9. A method as claimed in claim 8 wherein the routing information takes the form of a routing table that serves to distribute signalling gateway process identifiers over possible signalling link selector values included in the signalling messages.
 10. A method as claimed in claim 8 comprising repeatedly receiving the routing information from a signalling gateway process in messages that serve to indicate the availability of the point code concerned.
 11. A method as claimed claim 8 comprising initiating the repeated sending of the routing information by including a request in an audit message for a particular destination point code sent to a signalling gateway process.
 12. A method as claimed in claim 8 including a registration step requesting and receiving a signalling gateway process identifier from a signalling gateway process.
 13. A method as claimed in claim 12 wherein the registration request is included in a message indicating that the application server process is ready to receive signalling traffic.
 14. A signalling gateway element arranged to carry out a method as claimed in claim
 1. 15. A signalling gateway having a redundant set of signalling links to a signalling network and having a single point code, or set of point codes, therein, and comprising a plurality of signalling elements as claimed in claim 14, with each signalling element comprising a signalling unit to which a subset of the signalling links are connected.
 16. An application server element arranged to carry out a method as claimed in claim
 8. 17. A signalling system comprising a signalling gateway as claimed in claim 15 within a signalling network and having a single point code, or set of point codes, therein, the signalling gateway elements of the signalling gateway each having at least one connection with at least one application server element as claimed in claim
 15. 